Feat/otel memory semconv v0.1.0 - #2142

Extends the opt-in OTel integration so it now covers all three pillars
(traces, metrics, logs) and accepts trace context from MCP clients via
params._meta. An agent + MemPalace now share a single trace_id when
the client injects the W3C tracecontext headers.

Logs
  init_telemetry now also configures a LoggerProvider + OTLPLogExporter
  and bridges stdlib `logging` -> OTel via LoggingHandler attached to
  the `mempalace` logger (not root, so chromadb/posthog keep their
  existing stderr-only behavior). Every dispatch emits one structured
  record:
    "memory.dispatch tool=<tool_name> operation=<read|write|invalidate>"
  Records carry trace_id + span_id of the active span.

Trace context propagation
  New extract_trace_context(meta) parses W3C tracecontext headers
  from params._meta using TraceContextTextMapPropagator. memory_operation
  now accepts a parent_context parameter and starts the memory.<op>
  span as a child of the remote parent when supplied.

  The MCP dispatch wrapper in mcp_server.py extracts params._meta and
  passes it through, so any client that already owns a trace can fan
  into MemPalace without code changes.

  Sentinel object distinguishes "no parent" from "explicit None" so
  callers can pass either without ambiguity. Malformed headers fall
  back to a new trace and log at debug -- never raise.

Coverage
  + tests/test_telemetry.py (7 tests, no-op path)
  + 2 new DQL queries in docs/verification/mempalace-baseline.dql:
      Q7 logs with trace correlation by operation/tool
      Q8 end-to-end traces with multi-service fan-out
  M docs/observability.md -- logs section + reference client snippet
    that shows how to inject tracecontext into params._meta

Verified
  * full test suite: 190 mcp+searcher tests still pass, 7 new
    telemetry tests pass, ruff clean
  * Live tenant verification against dynatrace-dev:
    - 4 trace_ids each contain both `verify-agent` and
      `mempalace-mcp-e2e` services under one id (end-to-end
      propagation confirmed)
    - 4 `memory.dispatch tool=... operation=verify` log records
      landed in the logs pillar
  * No-op path: all new paths short-circuit when env unset

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…ace loggers

Two issues caught by end-to-end testing against a real mempalace-mcp
server (the in-process smoke from the previous commit didn't surface
either):

1. The structured `memory.dispatch` log line was emitted unconditionally
   from the dispatch wrapper. On the default install path (no
   OTEL_EXPORTER_OTLP_ENDPOINT) it leaked one INFO line per call to
   stderr -- noise with no consumer. Guard with `is_enabled()` so the
   line only fires when telemetry is on and there's somewhere for it
   to go.

2. The OTel LoggingHandler was only attached to the `mempalace` logger
   (dotted). But mcp_server.py / searcher.py / palace.py / miner.py /
   fact_checker.py / query_sanitizer.py / convo_miner.py all use the
   underscore name `mempalace_mcp`, which is NOT a child of the dotted
   tree. Result: the dispatch log line landed at OTel logger setup,
   the embedding init line landed, but none of the per-call dispatch
   logs reached OTLP. Attach the handler to all five MemPalace-owned
   logger names (`mempalace`, `mempalace_mcp`, `mempalace_graph`,
   `mempalace_hallways`, `mempalace_format_miner`).

Verified
  * tests/test_mcp_server.py + tests/test_telemetry.py: 167 pass
  * full suite: 2087 passed, 3 skipped
  * ruff clean
  * /tmp/e2e_mcp_optout.py drives a real mempalace-mcp subprocess with
    no OTel env -- stderr now free of `memory.dispatch` markers; module
    state confirms no LoggingHandler attached
  * /tmp/e2e_mcp_stdio.py drives a real mempalace-mcp subprocess with
    OTel pointed at dynatrace-dev. Confirmed in DT:
      - 4 spans: memory.read(3) + memory.write(1) keyed by memory.tool
      - 4 log lines: `memory.dispatch tool=X operation=Y` per call

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

The upstream fork sync (ISI-1920) added mempalace_checkpoint,
delete_by_source, delete_hallway, mine, list_hallways, and
kg_supersede. These were falling through operation_for_tool()'s
default ('read'), mislabeling four mutating tools and one fact
retraction. Classify them explicitly: checkpoint/delete_by_source/
delete_hallway/mine -> write, list_hallways -> read, kg_supersede
-> invalidate (atomic retire+write at a boundary, like kg_invalidate).

Also regenerates uv.lock for the [observability] extra against the
freshly synced dependency set.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…tream PR

Remove internal issue-tracker/project references (ISI-1068, ISI-1920,
"kagent") from the instrumentation docs and code comments ahead of the
upstream contribution, and format the telemetry dispatch lines to the
project's line-length=100 so `ruff format --check` passes in CI.

No behavior change: comment/whitespace only.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>